Detect PICO_COMPILER automatically when PICO_TOOLCHAIN_PATH is set#2937
Merged
Conversation
will-v-pi
reviewed
May 15, 2026
Co-authored-by: will-v-pi <108662275+will-v-pi@users.noreply.github.com>
will-v-pi
approved these changes
May 19, 2026
lurch
reviewed
May 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In passing with other compiler/clib related changes, this PR removes the need to specify
PICO_COMPILERwhen already specifyingPICO_TOOLCHAIN_PATHThus
PICO_DEFAULT_COMPILERis now only used if you have neither specifiedPICO_COMPILERor a toolchain file/path in which case you're basically looking in the users path environment at which point it's not a bad idea to pick one to look for (we could even help there, but that is a more involved change)